…nsumer

Found trying to upgrade DSAMind (scaffolded before this overhaul, compiled
skills stuck at pre-engine versions). setupAgents already unconditionally
refreshes every compiled SKILL.md, so re-running `init` looked like the
right update mechanism — but two bugs made it unsafe:

- The "does AGENTS.md already have a governance map" check was
  case-sensitive (`includes('Governance Map')`), while the engine's own
  detection (engine/parse.ts) is case-insensitive. A consumer's real heading
  ("## Governance map (entry point)") would read as absent, and init would
  append a duplicate generic block on top of an already-customized map.
- scaffold.ts wrote a blanket `.constitution/` line to the root .gitignore.
  events.ts's ensureOps writes its own nested .constitution/.gitignore
  specifically so events.jsonl/proposals stay committed while
  tone/compiles/board.html regenerate — a parent-directory ignore rule
  makes git never even look for that narrower exception (verified
  empirically), silently swallowing the delivery record and ratification
  queue the ops-plane design explicitly means to keep. Scoped the ignore to
  just the regenerable vendored copies (templates/, process/).

Verified: dry-run init against a full copy of DSAMind leaves CONSTITUTION.md/
AGENTS.md byte-identical and only rewrites the two skills that actually
changed upstream; a fresh-consumer dry run confirms events.jsonl is
stageable post-init. 25/25 tests (2 new).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Operator asked where the installed framework tooling version should be
tracked for a consumer (vs. the adopted-spec header pin vs. the product's
own ledger version), and invoked /propose-amendment on the idea. Drafted,
not ratified.

decisions/0002-version-axis-separation.md proposes extending Article F-II
("one home per rule") to name three distinct version facts and assign each
exactly one home: an instance's own Amendments Ledger version; the framework
spec version it has deliberately adopted (the CONSTITUTION.md header pin —
a ratified conformance claim, never auto-bumped past what's adopted); and
the framework tooling actually installed (the consumer's own package
manifest, e.g. package.json's @chinmaygit/constitution-cli entry — no new
field needed, confirming the operator's instinct). Evidenced by this
session's actual LEDGER-SYNC bug (fixed in code, not yet in law). Agreement-
only, with the reason on record — no catch-rate/friction hypothesis to
measure.

Explicitly did not rule on the operator's second idea (skills self-check
tooling currency and auto-run migrations): no concrete mechanism exists yet
to evaluate, and "auto-update tooling unattended" is a supply-chain-trust
question separate from version-tracking. Recorded as deferred follow-up
engineering work in the ADR's Consequences, not folded into this amendment.

CONSTITUTION.md itself is untouched — the drafted F-II text lives only in
the ADR; only ratify-amendment may write it into ratified law. decisions/
INDEX.md updated in the same change per decisions/AGENTS.md's own statute.
constitution audit + firewall both stay clean.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Operator feedback: the first draft was too dense to follow. Cut nested
parentheticals and legal-brief phrasing; kept the same three-axis ruling,
the same evidence, the same deferred item.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Ratified by Chinmay, 2026-07-05: "makes sense lets ratify this."

Extends Article F-II's Principle and Fitness (status: RATIFIED, unchanged)
to name three version facts and give each exactly one home: an instance's
own Amendments Ledger version, the framework spec version it has adopted
(the header pin -- a ratified claim, never bumped ahead of what's adopted),
and the framework tooling installed (the instance's own package manifest).
Purely additive -- nothing existing changed or was superseded.

Agreement-only, no pre-registered experiment -- there was no catch-rate or
friction hypothesis to measure. The operator's second idea (skills
auto-checking tooling currency and auto-migrating) is explicitly NOT part
of this amendment -- no mechanism exists yet to rule on it.

ADR-0002 flipped proposed -> accepted; decisions/INDEX.md updated. Version
bumped 0.17.2 -> 0.17.3 (header + cli/package.json via constitution doctor's
versionSync). Dogfood test's ADR count updated 1 -> 2. constitution.lock.json
re-accepted by the ratifier to close the F-IV drift this change opened.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>